Skip to content

chore(main): release 6.11.0 - #485

Merged
sebastiancorrea81 merged 2 commits into
mainfrom
release-please--branches--main
Aug 7, 2026
Merged

chore(main): release 6.11.0#485
sebastiancorrea81 merged 2 commits into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

6.11.0 (2026-08-07)

Features

  • agent: worker orchestration passthrough + chart 2.37.0 (#478) (6758a95)
  • service_definition: allow pinning specs to a tag or commit SHA (#470) (15b6d47)

Bug Fixes

  • azure/vnet: let a subnet declare its route table (#475) (d2a5faf)
  • docs: update usage example to a current release tag (a167934)
  • docs: update usage example to a current release tag (#484) (ed6f5b0)
  • nullplatform: fail template fetches that do not return 200 (#482) (c47b78b)

This PR was generated with Release Please. See documentation.

@gdrojas
gdrojas enabled auto-merge (squash) August 7, 2026 19:12
@gdrojas
gdrojas disabled auto-merge August 7, 2026 19:12
@sebastiancorrea81
sebastiancorrea81 merged commit 575b44a into main Aug 7, 2026
45 checks passed
@sebastiancorrea81
sebastiancorrea81 deleted the release-please--branches--main branch August 7, 2026 19:23
sebastiancorrea81 added a commit that referenced this pull request Aug 7, 2026
Second clean E2E test of the auto-merge chain after the release-please
race condition seen on #485 (unrelated to our fixes — see PR
discussion). Bumps the same stale example ref (v6.10.0 -> v6.11.0).
sebastiancorrea81 pushed a commit to nullplatform/helm-charts that referenced this pull request Aug 11, 2026
Two pushes to main landing within the ~45s auto-merge window let two
release-please runs overlap: one merges/creates the release PR while
another, already mid-flight with stale state, tries to update the PR that
just got merged and fails with "the pull request cannot be reopened".
Observed live on 2026-08-07 (PR #169/#170) and previously on
nullplatform/tofu-modules#485 with the same signature.

Adds the same top-level concurrency group tofu-modules' release.yml
already uses, so overlapping pushes queue instead of racing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants